feat: journal run lifecycle transitions - #608
Merged
Merged
Conversation
Co-Authored-By: Cursor <cursoragent@cursor.com> Co-Authored-By: Codex <codex@openai.com>
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: escoffier-labs/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This is slice 2 of #568. It connects the event journal added in #607 to existing run status writes while keeping
run.jsonauthoritative.BRIGADE_LIFECYCLE_JOURNAL=1.lifecycle_journal_requestedwithout creating a journal.Safety boundaries
Events contain only fields from the existing per-type allowlist. Raw errors, paths, prompts, provider output, and tool arguments do not enter lifecycle payloads. Journal errors fail closed before
run.jsonadvances.This slice does not add replay, recovery repair, doctor integration, shadow comparison, or journal authority.
Verification
./scripts/verify: 4,841 passed, 3 skipped, 82.92% coverage.